Magnum One/Magnum One (Mid-American Digital) (Disc Manufacturing).iso/d19/pcbgate2.arc/XNET.PRN

Text File | 1989-12-15 | 6.4 KB | 265 lines

              C r o s s N e t   M o d u l e   A   v 1 . 1 5


                (C)Copyright CDC Software Development 1989


                           All Rights Reserved





























                                        1










                         CrossNet - Introduction

       All  I have to say at this point is <WHEW!>.  It's taken a lot
     of blood sweating months to get CrossNet where it is.  Thanks to
     PCBGate,  a  lot  of  things  were made somewhat  easier.   But,
     unbeleivably, here it is finally.

       I  originally  designed it to  support *A* node to  echo  to.
     However,  it now supports up to 10,000 nodes and 1000 areas.   I
     know  that sounds a bit absurd, but, and this is in reference to
     many  aspects  of CrossNet,  it's full capabilities are  limited
     only  to the user applying it.  Sure, you can echo 1  conference
     with  10,000 nodes, or 1000 conferences with 10 nodes,  or...who
     knows?   As  you learn what  you have to work with, you'll  find
     many ways in which to apply it to your own needs.

       CrossNet is primarily designed for the PCBoard sysop who wants
     to carry Fido type echo conferences.  The advantage of this over
     PCBGate,  is  that CrossNet  tosses mail from, and creates  Fido
     type  packets.  In the scan process it will compress the packets
     and create Fido type netmail attach messages.  There's much more
     to  it,  as  you'll see,  but  for a simple setup the  above  is
     standard.

       If you want to get complicated, you can also cross conference,
     or  port conferences between a  Fido type network and a  PCBoard
     network.   Or,  operate  a  mail  Gate.  This is what  I  do  in
     practical  use between CanConfmail/Smartnet and  IMEX/Alternet.
     It's also partly why I wrote the program.

       But, without further adue, lets get on with it...
























                                        2










                           CrossNet - Overview

       First,  I'll fill you in on the environment, and how  CrossNet
     does what it does.  (further referred to as XNet)

       XNet uses 4 files to operate, which it will create for you:

     XNET.GLB    - Global Configuration
     NETNAME.CCF - Conference Configuration File
     NETNAME.ECF - Echo Configuration File
     NETNAME.LMR - Last Message Read Markers

       PCBGate  supported  100 areas.   But with this,  and  multiple
     networks  in  mind, XNet supports  up to 10 sets of 100  areas.
     Each  set has a name, such as "FIDONET".  Your config files then
     become  FIDONET.CCF etc. etc.  The configuration program manages
     these  for  you, menu driven  style so you don't go  crazy  with
     complexities.  Everything in one neat package.


     Global Configuration

       XNET.GLB  holds  the information  that XNet uses on  a  global
     basis  throught both processes, like the network names,  netmail
     area(s), runtime options, and other features.

     Conference Configuration Files

       More  on all of these files later, but basicly this file holds
     all  your conference definitions;  things like area names,  base
     paths, and other goodies.

     Echo Configuration Files

       These  hold  the  node  numbers  you are echoing to  for  each
     conference,  in  each network area  set.  You can echo up to  10
     nodes  per conference, however  a conference CAN be declared  as
     many times as possible.

     Last Message Read Markers

       These  keep  track of how  high in a respective message  base,
     XNet  has scanned.  It is maintained automaticly by Xnet, or can
     be edited by you of course, through the configuration program.











                                        3










                    CrossNet - Programs and Utilities

       Each  of  the following will  be covered in detail later,  but
     I'll  breeze  over what each  of them do.  The  following  files
     compose XNet:

     XNETCFG.EXE  - The Configuration Facility
     XNETSCAN.EXE - Mail Scanning Program
     XNETTOSS.EXE - Mail Tossing Program


     XNETCFG.EXE - Configuration

       ALL  of  XNet's configuration  files are managed through  this
     facility.   When run, you get the global configuration  screen.
     From  there,  you can  edit the conference configurations,  echo
     configurations,  and  the last  messge read markers quickly  and
     easily.

     XNETSCAN.EXE

       XNETSCAN  does  a  lot  of  things.  When run,  it  scans  the
     appropriate  message bases for new mail.  It takes this mail and
     writes  outbound .PKT packet files.  Once complete, it will scan
     the declared netmail directory for existing attach messages.  If
     any  exist, it'll update the current outgoing mail archive.   If
     none  exist, it'll create a netmail attach message, and  archive
     the packet for transmission via a network mailer program such as
     Binkley, FrontDoor, etc.  It will also update the .LMR file when
     complete.

     XNETTOSS.EXE

       XNETTOSS  will  search  the  specified inbound  directory  for
     arcmail  packets from your Fido echo feed.  If any are found, it
     will  decompress the .PKT files contained within, and toss  them
     to  your PCBoard message  bases directly.  If there are  netmail
     messages  within any packets you receive, they'll be written  as
     Fido messages in your netmail directory.


       That's  roughly the XNet environment.  It CAN work well, or it
     can  create havok.  Some aspects of XNet can make or break  your
     system,  and/or your reputation!   Pay special attention to  the
     following  configuration instructions, and all should go  well.
     Some special points that might get you into trouble will be well
     outlined.








                                        4